Sharing of content associated with events

ABSTRACT

Techniques are provided that allow users to collaborate in relationship to data views, application displays, applications or events. A user can type in a text view related to a specific view in an application display, and the information is shared with other users that take part in sharing that view. A user that expresses an interest in an event is notified about the event and has the capability to interact, in relation to the event, with other users (e.g. by text). The particular form of interaction (and sharing) can be selectively specified. This interaction is comparable to a dynamic bulletin board where the subject is event driven, and where a user can specify who are allowed to participate. In the case of an event interest(s), users specify their interest (e.g. in other user application events or system events) and the system automatically alerts them to the occurrence of the event.

RELATED INFORMATION

This application is a continuation under 35 U.S.C. §120 of U.S. patentapplication Ser. No. 11/746,547 filed May 9, 2007; which is acontinuation of U.S. patent application Ser. No. 09/998,517 filed Nov.29, 2001 (now U.S. Pat. No. 7,231,596), which in turn claims priority tothe following U.S. provisional applications: Provisional Application No.60/250,035 filed Nov. 29, 2000, Provisional Application No. 60/259,488filed Jan. 3, 2001, and Provisional Application No. 60/293,413 filed May24, 2001. Each these U.S. patent applications and U.S. Provisionalpatent applications is incorporated herein by reference as if fully setforth herein.

BACKGROUND OF THE INVENTION

The invention relates generally to methods and apparatus for providingscaleable, flexible, and interactive views of dynamically changing datastored in a cache, and more particularly, to a method and apparatus forflexibly interacting, controlling and collaborating, in real-time, thedisplay of data stored at a remote location and provided for interactivedisplay over a network or locally.

The invention relates to many Web-based applications and as one example,to financial fields, such as financial portfolio and market dataapplications. In particular, in order to function effectively, usersneed the proper tools to research, monitor, and analyze portfolio andmarket information, and to communicate with one another, with customersand with suppliers. Existing software systems currently provide onlypartial solutions to these needs. These systems do not provide aflexible, outsourced, real-time, collaborative, Web-based totalsolution. It is further important for these professionals to havereal-time tools which enable up-to-date data to be effectivelydisplayed, manipulated and shared in order to allow fully informed andcurrent decisions to be undertaken. Flexibility in user presentation canalso be important to understanding the data and the relationship betweendifferent data points and entities.

BRIEF DESCRIPTION OF DRAWINGS

The present invention is illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings. Otherfeatures and advantages of the invention will be apparent from thefollowing drawings, taken together with the description of theinvention, in which:

FIG. 1 is a general architectural description in accordance with theinvention;

FIG. 2 is a more detailed description of the server architecture inaccordance with the invention;

FIG. 3 is a first screen shot illustrating, a tabular view of data inaccordance with the invention;

FIG. 4 is a second screen shot illustrating a tabular presentation ofdata in accordance with the invention;

FIGS. 5A and 5B a yet further detailed diagram of the overall serverarchitecture in accordance with the failover mode of the invention;

FIG. 6 is a representation illustrating user display options;

FIG. 7 is a flow chart describing the general operation in accordancewith the operating method of the invention;

FIG. 8 is a more detailed flow chart description of system operation inaccordance with the invention;

FIG. 8A is a third screen shot illustrating a tabular presentation ofdata in which a selected trade can be modified or cancelled;

FIG. 8B is a fourth screen shot illustrating the next step in modifyingor canceling a selected trade;

FIG. 9 is a confirmation screen shot for modifying the selected trade;

FIG. 10 is a screen shot of a tabular presentation enabling the user tomodify a selected trade;

FIG. 11 is a screen shot illustrating a tabular presentation of dataaggregated by country;

FIG. 12 is a screen shot illustrating a tabular presentation of data asa result of “drill down” of the country aggregation illustrated in FIG.11;

FIG. 13 is a flow chart illustrating a particular implementationscenario shared application display methodology;

FIG. 14 is an alternate architecture for implementing the invention;

FIGS. 15-19 are screen shots illustrating column operations according toone aspect of the invention;

FIGS. 20A-20D represent a diagram of application display operations,allowing to hide and reveal different areas in the application display;

FIG. 21 is a diagram of an HTML based application;

FIG. 22 is a diagram of a browser based client application;

FIG. 22A is a diagram of a local client application;

FIG. 23A is a diagram of ViewServer implemented as a part of anApplicationServer;

FIG. 23B is a diagram of ViewServer, AnalyticalServer, DataServer andtransaction server implemented together as a part ofmodule/thread/process;

FIG. 23C is a diagram of ViewServer implemented as an operating systemprocess;

FIG. 24A is a diagram of an HTML based shared application;

FIG. 24B is a diagram of a browser based client shared application;

FIG. 24C is a diagram of a local client shared application;

FIGS. 25 A-C are diagrams showing moving a column in an HTML basedshared application;

FIGS. 26 A-C are diagrams showing moving a column in a client-basedshared application;

FIG. 27 is a diagram showing the display of different subsets of sharedapplication functionality at the same time;

FIG. 28 is a flowchart of the operations performed in FIGS. 25A-C;

FIG. 29 is a flowchart of the operations performed in of FIGS. 26A-C;

FIG. 30 A is a diagram of standalone shared applications;

FIG. 30 B is a diagram of multi-service shared applications;

FIGS. 31-1 and 31-2 are a flowchart illustrating a connection to theshared application;

FIG. 32 is a flowchart illustrating a process of application sharing;

FIG. 33 is a one-to-many sharing of a local application through thenetwork;

FIG. 34 is a flowchart illustrating application sharing by downloading ashared application (in whole or in part) to the local device for furthersharing;

FIG. 35 is a flowchart illustrating the operation of sharing shortcuts;

FIG. 36 is a flowchart illustrating a process for alerting a user aboutchanges in monitored conditions associated with the views;

FIG. 37 is a flowchart illustrating the process of setting parametersfor controlling application access;

FIG. 38 is a flowchart illustrating the process of sharing mediamessages in the system;

FIGS. 39A-B illustrate flowchart of the process of saving andsubsequently restoring views for further interaction;

FIGS. 40A-E are diagrams showing dynamic basic aggregation of a table;

FIGS. 41A-C are diagrams showing dynamic parameterized aggregation of atable;

FIGS. 42A-C are diagrams showing dynamic filtering of a table;

FIGS. 43A-I are diagrams showing a virtual column operations in a table;

FIGS. 44A-B are diagrams showing a login panel;

FIGS. 45A-H are diagrams showing various column charting operations;

FIGS. 46A-F are diagrams showing multi-column sort operations;

FIG. 47 is a flowchart illustrating column control bar operations;

FIGS. 48-1 and 48-2 are a flowchart illustrating the MatrixClickmethodology;

FIG. 49 is flowchart illustrating providing parameters for tablecolumns;

FIG. 50 illustrates an aggregation control panel according to one aspectof the invention;

FIGS. 51A and 51B illustrate filter control panels according to anaspect of the invention; and

FIG. 52 is a flowchart of the override function.

DESCRIPTION OF PARTICULAR EMBODIMENTS

Overall Architecture

Referring to FIG. 1, according to the invention, a general architectureof the system 10 includes a plurality of users 12 a, . . . 12 nconnecting to the display generation system 14 over a communicationnetwork 16, here the Internet. The users 12 typically employ computingdevices having a CPU, memory, storage, display, input devices,networking devices, etc., for communications with network 16. Othernetworks can include, for example an intranet or wireless network, localor with area networks, other public networks, etc. While other networkscan be employed, the ubiquitous nature of the Internet, and the abilityto connect to it make it an ideal communications medium with which toprovide user access to the interactive display generation system 14. Thedisplay generation system 14 has a data processing, acquisition, andcaching system 18 (here designated ViewTOTAL), which obtains; data fromexternal data sources 20 and which further obtains transactionalinformation from external transaction data sources 22. The users obtain,with this architecture, in accordance with the invention, a flexible,scaleable, real-time, interactive and collaborative view of configureddata from the system 18 as described in more detail below.

Each of the computing devices is interconnected by a network. Forsimplicity, it is presumed that the network is a Transmission ControlProtocol/Internet Protocol (TCP/IP) network. However, other networkingprotocols such as the Internet Control Message Protocol (ICMP) extensionto TCP/IP, Internetwork Packet eXchange (IPX), Sequenced Packet Exchange(SPX), AppleTalk, or the like can also be used. The network may be asingle physical link, or a logical structure crafted from a combinationof physical and non-physical data pathways (e.g., analog or digitaldialup connections, satellite links, etc.).

In one embodiment, the system employs the combination of web-clientsoftware on each user computing device and web server software on theserver. For example, the users can utilize web browsers and receiveactive HTML content (or JavaScript, Java, JScript, Active Server Page(ASP) files, ActiveX, Visual Basic, and the like) to interact with theserver; and the web server can be an Apache web server or a MicrosoftInternet Information Server.

When the system uses a web server, it is expected that Hypertext MarkupLanguage (HTML) tags (or the equivalent) are used to cause transfer ofpages to the client. (HTML is a document format based on the StandardGeneralized Markup Language (SMGL) that uses “tags” to flag formatting,structure, data access, etc.)

The system 18, referring to FIG. 2, has, in the illustrated embodiment aplurality of independent servers, having their own operating systems,connected to communication networks, for example, private networks 30,32, and which also connect to a database source 34 which can be either amass storage system having its own operating system and third partydatabase software, individual disk drives and a controller, or someother form of storage. The plurality of servers, and the privatenetworks 30 and 32, enable the system 18 to be resilient in the case offailure of one of the networks, and enable, as will be seen below,redundancy at the server level.

Other configurations of servers and networks can also be used. Thevarious servers noted above are in essence a set of object-orientedmodules that can be implemented in variety of ways such as an operatingsystem process, a thread in an operating system process, or a module inan operating system process, on one or multiple computers. There can beas a little as one instance of each server, or as many as needed systemwide. Such a system is usable with one network, or even without thenetwork if the whole system is running on one computing device, butmultiple networks can be deployed for the purpose of redundancy.

The distinction between the “servers” are functional, and a variety ofserver hybrids can be assembled to fit particular needs orcircumstances. In general DataServer deals with data gathering,AnalyticalServer deals with computations, TransactionServer deals withtransactions and ViewServer deals with keeping displayed views. Theservers typically cache the data in memory, therefore allowing quickaccess to their “clients” to the cached data. The ViewTOTAL can beassembled from any variety of combinations of the servers describedabove, while also having ApplicationServers for page generations and webservers for communicating with the users over the network. Indeed, it isalso possible to have all of the ViewTOTAL functionality implemented ona single server system rather than multiple smaller systems.

For example, ViewServer can be implemented as an operating systemprocess 2307 in FIG. 23C, or as a thread/module 2302 within anApplicationServer process 2301 in FIG. 23A, or combined as athread/module 2304 within one process 2303 with additional “servers”2305, and communicating over a software “bus” 2306 as illustrated inFIG. 23B.

In particular, the illustrated system 18 includes one or more webservers 40, one or more ApplicationServers 42, one or more ViewServers44, one or more AnalyticalServers 46, one or more DataServers 48 whichcan receive data from external data sources 20, and one or moretransaction servers 52 which can receive external transactions from anyof plurality of sources, such as external transaction sources 22, userinput, uploaded data (such as through FTP or the Web), as well as othersources.

The system architecture enables provision of real-time shared views withthe capability of interacting and manipulating application displaysbi-directionally between systems connected through a Web to Webconnection, a Web to local program connection, and a local program toWeb connection, as well as a local program to local program connectionthrough the Web.

In operation, referring to FIG. 7, the system 18 receives a request at100 from the network 16 at the web server 40. The web server receivesthe typically html page request and sends, at 102, the request to theApplicationServer 42 typically over one of the networks 30, 32. TheViewServers subscribe to updates from DataServer 48, transaction server52, and AnalyticalServer 46 as well as using data from the databaseserver 34.

The AnalyticalServer 46 asynchronously takes the information, processes,etc. and “calculates” the necessary data at 105, and delivers the datanecessary for assembling the page (at 106) which will be organized andstored by the ViewServer in its cache (step 106) returned to the userover the networks 30, 32 through the ViewServer 44.

The AnalyticalServer 46 asynchronously takes the information, processes,etc. and “calculates” the necessary data at 105. It publishes theresulting data over the networks 30, 32. ViewServer receives the data towhich it subscribed, and organizes and stores the data in its cache(step 106). The ApplicationServer assembles the page from the ViewServerdata (at 108) and the page is returned to the user over the networks 30,32 through the web server 40 at 112.

The AnalyticalServer recalculates only the changes in the received data,and the interval for recalculation is configurable, in the illustratedembodiment. Thus, for example, when the AnalyticalServer operates in a“HotCache” mode, it recalculates everything in real-time; when itoperates in a “WarmCache” mode, it recalculates in the timeout period;and when it operates in a “ColdCache” mode, it recalculates only whenrequested. It is the user decision or an automated priorityconfiguration system which decides which mode of operation to use. TheDataServer receives data updates from subscribed data sources. Oncereceived, the DataServer sends the data to its own subscribers and keepsa copy in its memory. The transaction server loads transactions fromavailable sources, aggregates them, and keeps them in memory. It alsosubscribes to new transactions, modifications and cancellations andnotifies its subscribers of the “updates” in stored data. The ViewServersubscribes to updates of the combination of data, analytics, andtransactions, and when the information is received, it organizes andstores it in cache. The information that ViewServer subscribes to iseither configurable globally (same information for all the users) orconfigurable as a per-user or per access identifier (see below). Theseand other configurations are kept by the system in a configurationdatabase. Referring to FIG. 21, in the case of HTML-based applications,the ViewServer 44 operates in a request-reply mode—it receives updaterequests from the user application (for example a web browser 2110) onthe client side and will automatically return an updated version of theweb data or “view” through the ApplicationServer 42 and web server 40.

Referring to FIG. 22, in the case of a client-based application, theViewServer 44 can operate either in a request—reply mode or in apublish-subscribe mode. In the publish-subscribe mode, client-basedapplication 2210 subscribes to receive updates through its associatedweb browser, and the ViewServer 44 publishes the updates through theApplicationServer 42 (since the client is, for example Java based, theweb server 40 may not needed). While commonly using the HTTP protocol tocommunicate with the client through the web server and/orApplicationServer, ViewServer can do it through other apparatus, withoutusing the web server and/or the ApplicationServer. For example, it canbe performed by having communication adapters in both ViewServer and theclient program that use a common communication protocol.

In any instance, the invention described herein is not dependent uponthe client program or how the client and server connect. In fact,referring to FIG. 22A, for a local client application, the locally basedapplication may communicate directly with the ViewServer rather thanprocessing through the ApplicationServer 42.

In the case of a local client-based application, the ViewServer may beimplemented as that application. The ViewServer keeps information in itscache memory 70 specifically for speeding the access to the displayeddata (at the user's display). When update occurs, the data status, on acell by cell basis, can be displayed to the user using a color schemecustomized for each user. Further, in appropriate circumstances, theViewServer can communicate directly with the local client-basedapplication.

Referring to FIG. 7 again, some of the data processing at 106 can resultfrom a user request, for example, a data override request, while otherof the data can be automatically processed at 106 as a result of theaddition of new data obtained by the DataServer 48 or the transactionserver 52. A client program can provide an automatic update usingpublish-subscribe paradigm, while HTML provides the data on request. TheViewServer organizes its cache 70 by displayed views of the application,from which it can then be passed, through the ApplicationServer wherethe web page is assembled at 108, to the web server, for delivery at 112over the network 16 and then to a user 12. Such an organization of datagreatly simplifies the page creation by the ApplicationServer, whichserves as a mere “formatter” of the data that is already organized forviewing. Referring to FIG. 3, the data can be presented in a typicaltabular format as illustrated by the screen shot of FIG. 3. This showsthe data from two instruments being presented, in real time, to theuser. The user can, as noted in the “Views” line 60, enable variousviews to be provided. Clicking on any of these elements will requestfrom the system 18 a new view. The view is automatically refreshed, asnoted above, at 114.

The ViewServers 44 each have their own cache 70 so that when requestinga currently used data view, it can be obtained without having to performany further analysis or obtain any further information, again, from thedatabase source 34. In a preferred embodiment, the table view, such asthat illustrated in FIG. 3 is efficiently updated by subscribing to andreceiving only changed data from relevant published data sources. In theillustrated particular embodiment of the invention, the cache 70 isorganized in terms of user requested data views, as illustrated in FIG.27.

According to the described embodiments, an application display is thedisplay from the application which can be, for example, a Graphical UserInterface (GUI) window or an HTML page. Each instance of the applicationdisplay can have application controls including navigation controls2010, information slice controls 2020, and a plurality of views such astable 80, graph 82, chart 84, news 86, alert 88, message 90 etc. (Seefor example FIG. 6). Each application can have one or more applicationdisplays as illustrated in FIG. 8A, 8B, 10, 11 and 12.

In a preferred embodiment of the invention, ViewServer will keep aversion identifier for each of its views. The view version identifierwill separately keep data changes and presentation changes. TheApplicationServer will keep the version identifier of its views as welland will compare its version of a requested view with the version keptin the ViewServer. For each data or presentation change, the viewassociated version identifier will be updated. If the version identifierfor particular view(s) in the ViewServer did not change since the lastview request by the application, the ApplicationServer can return itscached page for this view(s) without needing to reassemble the page.

In addition, referring to FIGS. 39A and 39B, views (one or multiple) canbe saved at 3901 (for example as reports) and stored by the system at3902. Later, the original or another user with access rights can accessthe saved view(s) at 3903. The system loads the saved views intoViewTOTAL, at 3904, and in particular, according to this embodiment ofthe invention, saved views need to be loaded by a DataServer whileupdating the AnalyticalServer and the user can interact with them, aswell as share them with other users at 3905.

Sharing Mechanism

The system enables sharing information among a group of userscommunicating through a network, in a way that allows the users to sharethe application look, feel, interaction and data, in whole or in part.

In a particular preferred implementation, according to this aspect ofthe invention, the system architecture provides shared applicationdisplays with a capability of interacting and manipulating suchapplication displays bi-directionally between systems connected througha network. The system implements bi-directional communication betweenuser applications and shared application service 2410 as illustrated inFIG. 24A for HTML based application, in FIG. 24B for a browser clientbased application, and in FIG. 24C for a local client.

For a client based program like a Java applet, the web server 40 isneeded to download its code, but it does not necessarily use a webserver, or even an application server 42 for communication. Furthermore,for a local client, even the application server 42 may not be needed.

The shared application service can be for example an operating systemprocess, an operating system thread, or a module within theprocess/thread. The shared application service can reside on a “server”or it can be downloaded from application storage 3304, in whole or inpart to the client, and can be further shared with other users usingarchitecture illustrated in FIG. 33. One shared application can havemultiple services and can serve multiple user groups simultaneously.Users can join and leave the sharing group at any time.

There are a number of sharing modes that can be employed, eitherindividually or in combination by a system. A data sharing mode refersto sharing a common set of data, so that when data changes are made byone of the users, or the shared application service data is updatedthrough its internal computations or application external data sources,the change is reflected in the shared application service and will beseen by all other users of the application service when they view anysuch affected display or displays.

Data sharing allows an independent arrangement of shared data to beviewed by each user. For example, moving a column in a data sharingarrangement will not affect the shared application service or other userviews, but an update of underlying shared data will. Typically in thecase of data sharing, the system will create a new application serviceinstance for each new user, as illustrated in FIG. 31.

View sharing refers to the way applications look, feel, and interact,and are shared among the users, so if, for example, a column is moved ina shared view, the column will be moved in the shared application andeach other users' applications.

Typically, there is only one shared application service instance in theview sharing mode, even if there are multiple users authorized to accessthis particular service. Referring to FIG. 30A, a shared applicationservice can be implemented as a standalone application 3001 instantiatedfor each user (or user group in the case of identical sharing within agroup) or, referring to FIG. 30B, a multi-service application 3002 thatprovides configurable application functionality to each user (or usergroup in case of identical sharing within a group). Each instance ofapplication service (either shared or not) has a unique globalidentifier 3010 which is used to by other system components, such as anApplicationServer, to address the service.

A particular embodiment of such a shared application implementationaccording to the invention, is a ViewServer, which provides informationview services to the user applications. The ViewServer organization ofits cache, in terms of application views, enables sharing of applicationdisplays among multiple users. When a view in a ViewServer changes as aresult of an information update or user manipulation, all the users thatshare this view in a view sharing mode, will receive a new updated view(either in real-time or at the next display refresh). The users thatshare in a data sharing mode will receive updates only in the case of aninformation update.

In the case of restricted access to an application the system canprovide application access (and potential sharing) in one of two ways:the first method provides a username and or password. For example, asshown in FIG. 44A, the system displays username field 4410, passwordfield 4420 (use of a password field may not be always necessary) andlogin button 4430. Upon entering these fields, the user activates thelogin button 4430. If the system authorizes login, the user is allowedto use the application. When using the same username and password, itessentially allows login to the same application, and enable completesharing of the application. In the second method system create (as aresult of a user request or an automatic system initialization) anidentifier for such an access (to be called “access identifier”) andstores the access identifier with its associated information, which willspecify the application services allowed to the user or users of thatidentifier. An identifier can thus be provided for each user (useridentifier) or the whole group (group identifier). The identifier canprovide an access to information (that can be static or dynamic) in thesystem. The accessed application service can be shared with other users(in whole or in part), or be provided on a standalone basis. The accessidentifier can be implemented, for example, as a URL link. Alternativeaccess identifier implementation could be a username and passwordcombination, in whole or in part. When the identifier is user specificand requires a password, use of that identifier should prompt only forthe password field 4420 as shown in FIG. 44B, and save unnecessarytyping of user name by the user.

Because of the nature of web based applications, accessing oneapplication may allow access to multiple applications, and the otherapplications can be accessible through a URL link in the originalapplication.

When implemented by use of a URL (a uniform resource locator), thesystem sends the access identifier (URL) to the user. The user opens itsmessage (for example email, or a page in his application, appearing as aURL link). The user clicks on the link and brings the page to view.After a successful login (if a link requires authorization), the userenters his login information. If authorized by a system, he is allowedlogin to the application. The system connects the user to theapplication service which can be used according to the accessidentifier.

Referring to FIG. 32, when a user decides to share his application, inwhole or in part, with additional users over the network at 3210, theuser can specify which parts of application to share, any restrictionson how the shared application can be used, and for how long to share theapplication (at 3220). The user also decides who shall have access tothe shared application (at 3220). The system then creates accessidentifier and stores it with related parameters at 3230. The systemthen sends a sharing message to the specified recipients at 3240. Afteropening the received message, recipients get access to sharedapplication and can then use it (at 3250). The user and recipients (at3255) are now sharing the application. In addition, the user canproactively monitor use of the application by other users anddynamically change any attributes associated with sharing theapplication (at 3260).

The application can provide the user with “shortcuts” which will allowto the user perform sharing more effectively. There are a number ofshortcuts, among them a basic shortcut and a parameterized shortcut. Thebasic shortcut contains all the parameters for sharing and will beactivated under control of one action. The parameterized shortcut hassome parameters preset, and some parameters that need to be provided.

The user can create the shortcuts and store them in the system forfurther use. In a preferred embodiment according to the invention, abasic shortcut will contain an access identifier, to eliminate the needto create an access identifier each time, when all the parameters arealready known. The parameters for implementing sharing can be providedfrom a combination of default values, and/or the previous usage historyfor the parameter, or can be provided by user.

For example, referring to FIG. 35, the application can have Share View,Share Page, and Share Application shortcuts that allow the user tospecify what part of the application to share. In some cases, the usercan specify, in one action 3501, what functionality to share and withwhom.

More specifically, for example, in the case of technical support, theuser can use help “shortcuts” such as View Help, Page Help, andApplication Help. The shortcuts can be implemented, for example, aslinks or voice activated commands. Activating the View Help “shortcut”will cause an access identifier for the current view either to beextracted from shortcut at 3508 or to be created from the shortcut at3502 and sent automatically at 3505 to technical support.

The technical support person who accesses a message with the accessidentifier will receive access to the specified user view at 3506 (whichcan be continuously updated). This will make the support process muchmore efficient, because the support person can instantly see and shareat 3507 (either in the data or the view sharing mode) the informationwith which the user needs help.

In one particular embodiment of the invention the method for using ashared application can be implemented, as illustrated in FIGS. 31-1 and31-2 using the following steps:

Connect to the shared application by providing an access identifier (forexample a URL) (step 3101);

If the identifier requires either a user identifier and/or password(step 3102), the user enters this information (step 3102-1);

If access granted at 3103, then if the identifier indicates a datasharing mode (step 3104), go to step 3105;

Otherwise the system checks for the existence of an instance of therequired application service at step 3106;

If no application service instance exists go to step 3105; otherwise thesystem connects (step 3107) to an existing application service instance;

In the step 3105 the system creates a new instance of the applicationservice using the configuration associated with the access identifierand connects to the service instance;

The ApplicationServer (in the case of an HTML application), or otherwisethe client-based application then creates, in step 3108, requiredapplication displays using the configuration associated with the accessidentifier; (the creation of application displays is affected becausethere are many displays and only few are required at a time).

The information is acquired from the shared application, in step 3109,using either a request/reply or a publish/subscribe mechanism;

The information is filtered as necessary at 3110;

If the application is an HTML application, the application display, withthe information, is constructed at 3112; Otherwise, the applicationupdates its displays with new information at 3115; If the user requestsa new application display at 3113 the systems goes to 3108; Otherwisethe system then loops to update or refresh, as necessary, the shareddisplay depending upon the user application type as indicated in step3112 (for example in an HTML implemented application the system loops tostep 3108, while in client-based implementation the system loops to thestep 3109);

The filtering operation of shared information, applied at 3110 can beperformed in either the shared application service or in theApplicationServer. When the ApplicationServer performs the filtering,the shared application service will provide all of the information foreach application display and the ApplicationServer will filter theinformation for each user. This approach makes it easy to implement theshared application service since it is not aware of the applicationdisplay filtering. The drawback is that unnecessary information ispassed to the ApplicationServer.

Another approach is to implement filtering in the shared applicationservice. This approach minimizes the data transferred to theApplicationServer but introduces more complexity in the applicationservice. To make data access and manipulation effective and fast, sharedapplications can store information in terms of user data views, so itcan rapidly make updates according to user requests and distribute theupdated data to the users. Each user application display, which can be apage (in HTML) or a window (in case of client-based applications), andeach view within an application display, will be represented bycorresponding objects in the shared application.

In a particular embodiment of the invention, the manipulation actionsand parameters which result, for example in the column manipulationsdescribed above, will be sent to the ViewServer for further processing.

Referring to FIGS. 25A-C and 26A-C, (and the corresponding flow chartsof FIGS. 28, 29) suppose a user wants to move a column in a table. Theshared application, in this case, will retain information, in cache, interms of the user views. The shared application can store theinformation in a table format, which will make it easier for theapplication to move specified columns and also to update the views ofother users.

For example, in an HTML user application, referring to FIG. 25A and FIG.28, a table view 2530, in a user application 2510 and a table view 2540in a shared application 2520 are illustrated, before moving a column. InFIG. 25B, the user selects the operation which will move column B to theright of column C (step 2810), and this instruction is passed to theshared application 2520 (step 2820) which implements the move as shown2550 (step 2830); The user table view 2530, at this point in timeremains the same. Referring to FIG. 25C, the next time the user page isrefreshed (step 2840), it will reflect in the new view, shown at 2560,the column move operation, already performed in shared application (step2850).

In a client-based user application, now referring to FIG. 26A and FIG.29, a table view 2630 in a user application 2610 and a table view 2640in a shared application 2620 show the data presentation before moving acolumn. Referring to FIG. 26B, a user selects an operation which willmove column B to the right of column C (step 2910). This column is movedat the user application 2610 as shown at 2650 (step 2920); while theshared application table view 2640 remains the same. Referring to FIG.26C, the instruction is then passed to the shared application 2620 (step2930), which moves its table column B as shown at 2660 (step 2940).

Referring to FIG. 27, different users can be given access to differentsubsets of shared application functionality (typically the views) at thesame time. Thus, as shown in FIG. 27, a shared application 2710 hasopened several views A,B,C,D. Three user applications 2720, 2722, 2724connect to the network 16. In accordance with the invention, differentones of the user applications will typically have access to differentviews of shared application. Thus, as shown in this example, userapplication 2720, has access to views A and B; user application 2722 hasaccess to views B, C and D; and user application 2724 has access toviews B and D. According to this aspect of the invention, a change madein view B, will be seen by all the user applications; while a change inview D will only be seen by the other user application 2724 or 2722,respectively (typically instantly in a client-based application or at anext refresh in an HTML-based application). Changes in view A will beseen only by user application 2720.

The shared application service also allows users to interactively shareinformation in different media forms such as data views (table,charts/graphs), text-like views (news, alerts, messages), voice andvideo. Once an application is shared for example, through the dataviews, the sharing participants can collaborate further through the useof text, voice and/or video. Upon access to the shared applicationservice, then, the user will be able to read and write text, speak andhear using voice, and show and watch video, as well as view theassociated application. (When the shared application service is sharingviews, it is acting as a shared ViewServer.)

Users can thus collaborate using media such as text, voice and video inrelationship to the combination of data views, application displays, theapplications themselves, and events, or can collaborate independent ofthem. For example, in case of a text/data-view relationship, referringto FIG. 38, the user can type in the text view at 3801 related to thespecific view in the application display, and the information is sent tothe shared application service at 3802, and that text also can be sharedwith other users that take part in sharing that view at 3803. This way,users can not only share the data and views, but also can includecommentary relevant to the shared views.

In another example, in the case of media/event relationship, there is aheadline about particular event. A user that expresses an interest tointeract about the event will be notified about the event and will havethe capability to interact, in relation to the event, with other users(by text, through voice or video). The particular form of interaction(and sharing) can be selectively specified. This is comparable to adynamic bulletin board, where the subject is event driven, and where theuser can specify who are allowed to participate. The interactions can berecorded and replayed later. In the case of an event interest(s), theusers specify their interest (which can be in either other userapplication events or system events) and the system automatically alertsthem to the occurrence of the event. Furthermore, the system can providenot just the alert but also additional information (such as theassociated view(s)), so that the alert can be related, in context, withthat additional information. For example, messages with a correspondingtext description can be provided automatically if triggered byconditions that have been specified by the user. In this way, a user canproactively watch a limited number of views, but once there are changesthat occur in other views of interest, the user will receive a messagethat includes an access identifier to such other view or views. Theidentifier can point to or provide an access to a snapshot of a view atthe triggered moment as well real-time views. The view typicallycontains a combination of table views, chart/graph views, news, etc.

Referring now to FIG. 36, the user specifies, at 3601, anyassociation(s) among one or more conditions (a condition group) and theviews to be sent to him and/or other users when such condition(s) occur.The user can further specify other attributes, at 3602, such as the sizeand location of the views to be displayed, and whether to display theseviews automatically or under control of the user. The system creates anidentifier and the associated information for each condition orcondition group (users, views, view size, and location, etc) and storesthe identifier and information (at 3603). The system monitors for theoccurrence of such condition/condition group at 3604. Whencondition/condition group occurs, the system sends the access identifierto the user(s) at 3605. The views can then be displayed to the userautomatically or manually under user control (at 3606). It should benoted, that the user, at any time, can modify the attributes of anaccess identifier at 3607.

Referring to FIG. 37, once initiated at 3701, the system tests, at 3702,whether sharing is to be implemented. If sharing is to be implemented,the user then determines, at 3703 whether any default parameters will becustomized. If none are to be customized, the user proceeds to 3706,otherwise the user specifies and customizes those parameters at 3705.The user then determines whether any other parameters need to bespecified at 3706. If yes, the user specifies and sets those parametersat 3707 after which the system implements the sharing mode at 3708. Ifno parameters are to be specified at 3706 the system proceeds toimplement the sharing mode at 3708.

The application access identifier can be generated automatically by thesystem based on the identity of receiver, or can be generated using userspecified information at the time of generation. In either instance, itis then sent to the recipients by the system. The sender of theidentifier will be able to see what identifiers he sent and candynamically change access of a recipient by modifying parametersassociated with the identifier. The system will selectively createapplication views and displays based on these parameters. Such aper-user customization will provide a subset of shared applicationfunctionality to such a user.

The user can specify application access parameters or use defaultparameters (which can be further overwritten). Some or all of theparameters can have a default value on a per user basis. The system willcreate an access identifier and will store the following parametersassociated with the identifier. In a typical implementation, the systemparameters which are used are:

For how long the identifier is valid?

Which users can use the identifier?

Does the identifier usage requires further information?

-   -   such password and/or user ID?

What information is accessible?

-   -   information slices;    -   view groups and views;    -   columns within the view;    -   chart/graph type available;    -   capability to make transactions;

What content is displayed?

-   -   Sensitive content can be “blacked-out”

What kind of interaction is allowed:

-   -   for example, moving columns, sorting, etc.

Is data sharing or view sharing implemented?

What components of the application display are shared?

Can further sharing of the application be allowed?

The system will keep a history of sharing and can provide a user withthe choice of previously selected used parameters.

In other aspects of the invention, a number of implementations and usesof the inventive architecture are described below.

In one particular embodiment, the system can be deployed locally and theshared application is implemented as a local application with agraphical user interface (GUI). This configuration of the softwareallows a bi-directional interaction between in-house (local)applications and Internet/Intranet (web-based) applications where anyoperation in one program is automatically reflected in another programthrough the use of shared views. For example, sorting or moving a columnby a first in-house user of a group, will result in an updated(sorted/moved) display on the web-based application of a second user ofthe group, and vice versa. Further, when the user using web-basedapplication accesses a new application display which has not yet beenviewed by the local user, it will cause a new window to pop up on thelocal user's screen. Also, in another example, when the user using aweb-based application, changes an information slice (such as a portfoliowhich he is viewing in the case of a financial application), the resultwill be displayed in the local application, thus showing thatinformation slice (portfolio) to the local user.

This application display methodology can be advantageous for users whowant to control proprietary data and applications locally, and at thesame time, have the flexibility of interactively remotely accessing thedata through the network in exactly same way as though they were local.

The system thus also provides a message sharing platform. Referring toFIG. 13, as one example, users can go to an outside meeting (step 500)and yet access all of the application views which are available on thecorresponding local application, in the same way that it existed, at hiscomputer, when he left it. (step 502). Further, he can access the views,interactively, from any computer with internet access and without anysetup delay. In addition, the user can interact and modify the viewsfrom the remote location, (step 504), and when the user returns from themeeting (step 506) he will find, at his display device, the views he waswatching before he left and/or any new/modified views created during hisoutside visit (step 508).

In another example, the user can monitor from home any of his peers andcan selectively look at any of the application displays of his peers inthe real-time. This is accomplished because the ViewServer keepsinformation regarding the views which were accessed and used.Essentially then, the methodology of the invention, using thisstructure, provides the capability of sharing interactive real-timeapplication views from any location at any time.

In a similar manner, two or more web-based applications can interactthrough shared application displays in a shared application/ViewServerarchitecture (FIG. 2) and where the shared application/ViewServer can beeither a local application or a server application.

Accordingly, a typical architecture for implementing shared views andmaintaining the applications “in-house” is illustrated in FIG. 14. Inaccordance with this architectural aspect of the invention, a pluralityof local computing devices 530 connect to a private network or intranet540 and run the applications “locally”. There is provided a connectionbetween the private network (for example a local area network or virtualprivate network) and the public network (for example the Internet orintranet) 550. Remote computing devices 560 connect over the publicnetwork to the private network 540. In a similar way if network 550represents an intranet then local users can access and share other localuser applications of others. Another example is a one-to-many sharinginteraction where the user runs his local application on his device(which can be, for example, a computer, laptop or wireless PDA) and canshare the application with other users through the network. This way theuser is in complete control of the application sharing because itresides on his device and he can, at any point of time, physicallydisconnect other users or terminate the program.

Referring to FIG. 33, an operation according to one embodiment of theinvention, a user device 12Z, in this particular embodiment, will have aweb server 40, an ApplicationServer 42 as well as a shared application3303. In the case that the application is not initially located on theuser device (such Java applet or C# based program, for example), astested at 3410 (FIG. 34), it can be downloaded with associated resourcesat 3430 from other locations such as application storage 3340. Once theapplication is on the user device, the user can send a message to otherusers 12-12 n at 3440 which will contain an identifier for the sharingaccess. The sharing users will utilize this identifier at 3440 to loginto the user device through the web server and share the application. Insome embodiments of this aspect of the invention, depending upon thenature of the shared application and the network 16, the WebServer andApplicationServer may not be needed.

Interactive Table

HTML is a widely used standard but it does not have the built-infacilities to interactively manipulate table content especially whenthis content is dynamically updated. According to the invention,therefore, column, row, and cell interactivity can be provided tomanipulate the table content. For convenience, most of the interactivityand manipulations described here relate to columns of a table, howeverthey are equally applicable to manipulations and interactivity among therows of a table. Many of the manipulation herein described can also beadvantageously applied to non-HTML tables.

Column Operations

As illustrated in FIG. 3, there are included in the display variouscontrol “buttons.” In this embodiment, selecting a control button willvisually mark it and deselecting it will remove the visual marking ofthe control button. In addition, when there is only one control ofparticular type that can be selected at a time in a given table,selecting another control of the same type will deselect the previouscontrol.

Such control will be called uni-column control. For example, selecting acolumn to move can be applied only to one column at a time.

On the other hand, a column filter can be applied to multiple columnsand as such it is a multi-column control. Selecting second multi-columncontrol will not deselect a first one. Some of the controls can beconfigured as either uni-column, or multi-column, for example columnsort. Multi-column controls will have in addition to controls associatedwith columns, a per table control which allows selecting/deselecting allthe operation that apply to a selected controls of that type.

There are a few practical reasons, for having such a control. First, itallows deselect all the operations of particular type within one action,without the need to individually deselect controls in each selectedcolumn. Second, after deselection, it will allow selection of allpreviously unselected controls at once, thus keeping a history of lastmulti-column selection of that type.

Also, the table will keep a history of multi-column operations, thusallowing the user to easily choose from previous operations. For eachselected multi-column control of particular type, an associatedper-table control of that type will be presented in a per table controlpanel. This is illustrated in FIG. 45G and FIG. 45H.

Buttons 62 a, 62 b, . . . , 62 m, in this embodiment, for example, whenclicked upon, will automatically enable a rearrangement of the views, sothat the column clicked upon is sorted and visually marked, andpresented either in ascending (sort up) or descending (sort down) order.The marked column control button can be visually marked (such asenlarged, and/or highlighted or otherwise distinguished). Any of thecolumns can be selected and will control the reorientation of each ofthe rows into an order according to that column.

In addition, an additional control button such as a button 62 x separatefrom the table (as illustrated) can be used to lock the particular sortselected (sort lock), no matter to which of the columns the sortrelates. Alternatively, a lock button can be displayed adjacent to anactuated button 62 a, 62 b . . . 62 m. The sort lock control button willappear only after a sort was performed in the table. Once locked, thatorder will be maintained across the entire table and the rows rearrangedif updated data requires such a rearrangement in rows. The sort can beimplemented to automatically take place as the data is dynamicallyupdated. Note that in accordance with this embodiment of the invention,only one column can be selected at a time to control the sort operation.To indicate such a sort lock, the sort lock control button will bevisually marked (such as highlighted and/or enlarged) in the column,that was lock sorted. Actuating that control button, deselects the sortlock function, leaving the visual appearance of that button in itsnormal state. Further, selecting the sort control button in any othercolumn, while one is already activated, will deselect the previous sortlock, and enable a new sort lock associated with the newly sortedcolumn.

Alternative embodiment of the invention is multi-column sort, andmulti-column sort lock/unlock. For example, as shown in FIG. 46A table4610 presented, having three columns A (alphanumeric column), B (datecolumn, where format used is Month/Day/Year) and numeric column C. Eachof the columns has associated sort controls, such as sort ascendingcontrol 4602 and sort descending control 4603 in column A. Selectingcontrol 4602 in FIG. 46A sorts table 4610 by ascending order of column Aresulting in table 4620, while visually marking control 4602A, as shownin FIG. 46B. Selecting control 4604 in FIG. 46B sorts table 4620 byascending order of column A and then ascending order of column B,resulting in table 4630, while visually marking controls 4602A and4604A, as shown in FIG. 46C. Selecting control 4606 in FIG. 46C sortstable 4620 by ascending order of column A, then ascending order ofcolumn B and then ascending order of column C, resulting in table 4640,while visually marking controls 4602A, 4604A and 4606A, as shown in FIG.46D. In one embodiment, the sort order among the columns in themulti-column sort, is established by the relative positions of thecolumns. For example, moving column B in FIG. 46D to the first column,moves column A to the second column, and the sort among the columns isdone in the following order: first by ascending order of column B, thenby ascending order of column A and then by ascending order of column C,resulting in table 4650, as shown in FIG. 46E. Selecting sort descendingcontrol 4608 in column C, results in table 4660, as shown in FIG. 46F,where visually marking is removed from control 4606A (indicated at 4606)and visually marking control is added to control 4608 as indicated at4608A. Multi-column sort can be also sort locked, resulting indynamically keeping the established sort order while data in the tableis dynamically updated. Multi-column sort lock control will be typicallylocated in per-table control bar described earlier.

In the preferred embodiment of the invention, the user action and itsparameters are passed to and maintained on the ViewServer. For example,sort order will be maintained on the ViewServer, so that the columnswill be resorted upon the presentation to the user as the data changes.This allows for the same sort order to be maintained even where the userlogs out from one location and logs in from a separate location. Thisadvantageously saves the user from needing to repeat the steps whichrelate to his preferred “view” of the data as the user may move from onelocation and log on at another.

In addition, other, or hidden, control buttons can be displayed toscroll and move columns to the left and/or right. Accordingly, in onegeneral embodiment of the invention, one can use a “control button” suchas the control button 63 illustrated in FIG. 3 to open up, or activate,a new series of control buttons, like control buttons 65, which, whenclicked upon, selects a column and enables that column to be moved tothe left or the right one or more columns. For example, one of thepreviously hidden control buttons, when clicked upon, can open up aseries of buttons (like button 65), or those buttons 65 can be displayedby default. Then, the first button clicked identifies a column to bemoved while a second button clicked identifies where to move the column.The data can then be rearranged in the view. Also, in this manner, thedata presentation can be flexibly altered, in an automatic “click anddrag” or other manner to move related column data so that it is adjacentto each other. Also, in this manner, different views of the data can beautomatically obtained, in real time, to enable view analysis and/orotherwise help the decision process. To accomplish the new view, therequested “button” click is sent by the user's browser back through thenetwork 16 to the system 18 where the new view and page can be assembledand obtained.

For example, according to one embodiment of the invention, each columncan have a Control Button to select the column to be controlled, andMoveTo (<- ->) Buttons (such as buttons 630, 632 to be described later),and Sort Up/Lock/Down buttons. Clicking on the Sort button willrearrange the view so that the column clicked upon is presented eitherin ascending or descending order. If the Control Button in the column isclicked on, then that column will be identified visually as the selectedcolumn and will cause the display of MoveTo buttons on all the columnsexcept the selected column. A TableView Control Button, when clicked,shows the Column Control Button and Column MoveTo (<- ->) Buttons. Ifthe ColumnMoveTo Button of a column is clicked, this column will bemoved (if possible) one column to the right if the -> button clicked, orone column to the left if the <- button was clicked. If the ColumnControl Button is clicked, the subsequent clicking of a <- or -< buttonon a different column causes the selected column to move accordingly tothe left or the right of the clicked on column. Also, according toanother embodiment of the invention, each column can have a ControlButton that allows the user to hide that column, as well as button(s) toreveal adjacent hidden columns.

In a particularly preferred embodiment of the invention, referring toFIG. 15, the GUI presentation has a column control actuation button 600.This mechanism can turn on (cause to be displayed) “column controls” inthe column headers. (FIG. 16). These controls 602, 604, 606, . . . canbe added or removed by actuating the column control actuation button600. Thus when this control is turned on, as in FIG. 16, on, the columnswill have controls 602, 604, 606, . . . in the headers, and when thecontrol 600 is turned off (FIG. 15), the column controls 602, 604, 606,. . . will disappear. In this way, the system preserves space on theuser screen and does not show the control buttons when they are notneeded. Thus, the system avoids cluttering the screen, yet provides theflexibility to add the controls with one actuation. (For simplicity, inthe figures, upon activation of button 600 only those controls needed tounderstand the figures have been illustrated. It is to be understoodthat in actual system, all of the control buttons that were configuredto be displayed, will be presented.)

The column controls of FIG. 16 allow the user to rapidly and effectivelyperform a sophisticated manipulation of columns, such as column sort,sort lock, move, hide and reveal, aggregation, filtering, charting andmore. These controls allow direct manipulation of information withoutdisplaying any additional screens, so that the user can continuouslywatch the current view. The system will also have a column control bar,which, as shown in FIG. 47, provides the ability to selectively indicatewhich of the column controls will appear (at 4710), and in whatarrangement (at 4720), when the column controls are displayed.

Once the control button 600 is in its “on” state (FIG. 16), severaloperations can be implemented. In one such operation, the move select<-> button 620 indicates a column to move. Clicking on the <-> buttonwill select the column for a move and the selected button will bevisually marked (for example enlarged). All of the columns, except theselected column will show “now Move To <.vertline. .vertline.>” arrows630, 632 (FIG. 17).

In another aspect, either of the <.vertline. .vertline.> buttons 630,632 will move the selected column respectively to the left/right of theclicked column. Thus, in FIG. 17, button 640 was selected, with theresult shown in FIG. 18. Further, clicking the <-> button 620 on theselected column will deselect it, and the visually marking of the button620 will be removed and the “move to” controls 630, 632 in FIG. 17 inall other columns will disappear. Clicking the <-> on any other columnwill deselect the previous column as the column to move and will selectthe “other” column as the column to move.

In addition, one of the column control buttons “-” is used to hide thatcolumn. Selecting the “-” control will cause that column to disappearfrom the table. Such a “hidden” column will be indicated by a newlyappearing “+” button in the column that was adjacent to the “hidden”column. Selecting the “+” button will “reveal” the “hidden” column. Itis possible that a given column will have more then one “+” which willindicate there are multiple hidden columns adjacent to that column. Theuser can selectively “reveal” a specific column whose identity can bedisplayed while rolling a mouse over the “+” buttons.

Aggregation

Referring to FIG. 40A, other controls for effecting other manipulationsof the table can be made visible by clicking on button 600. The controlbuttons {’4001, as shown at FIG. 40A, are used for preset or dynamicaggregation of the table by the content of the associated column whenselected. Beside a preset aggregation table, where the aggregationcriteria are fixed, the table can be dynamically aggregated by anycolumn in the table. When a column is selected for aggregation byactivating ‘{’, the aggregate control 4001 will be visually marked (forexample enlarged and/or highlighted) to indicate the selection, as shownat 4002 (FIG. 40B). If that column was not a first column, theaggregated column will become the first column. In the newly createdaggregated table, only the numeric data columns that can be aggregatedwill be presented. When aggregated view 4020 is drilled down upon, byactivating a folder-like control 4003A, for a row 4006 in the aggregatedcolumn, the resulting detail table 4040 (FIG. 40D) for that row willpresent all of the columns of data from the original table 4010. Theoriginal table 4010 will again be displayed after deselecting theselected ‘{’ control 4002. Alternatively, selecting aggregation of adifferent column, for example column D in table 4020 will display a newaggregated table 4050 (FIG. 40E). In both cases, the visually marking ofpreviously selected control 4002 will be removed. There can be at leasttwo types of aggregation: basic aggregation and parameterizedaggregation (for example, range aggregation where aggregation isperformed based on specified ranges). Basic aggregation uses solely acolumn content to group the information. For example, in FIG. 40A, basicaggregation is applied to column B in the table 4010.

As a result, a new table 4020 is generated containing only theaggregated column B and derived numeric columns, such as shown incolumns in C and D. The column B becomes a first column. Original columnA, which contained text information is not included in table view 4020.In FIG. 40B, five aggregated groups are created in column B labeled 500,700, 800, 850 and 1100, and contain folder-like controls 4003. Anaggregation control 4002 in column B visually indicates that aggregationis performed using that column. Correspondingly, the content of aselected row in column C in table 4020 is the result of straightaddition of the values in column C for the rows having a value in columnB of table 4010 equal to the value in column B of the selected row intable 4020. Further manipulation of the resulting aggregated columns,using a selected function, is possible. For example, in FIG. 40C anaveraging function is applied to the underlying data of column Cresulting in average values as illustrated in column C avg. For example,the value of C avg in the row corresponding to the folder labeled 1100of FIG. 40C is an average value of the values in column C in the rows ofFIG. 40A, which contain value 1100 in column B. As noted above, otherfunctions can be applied to the underlying data of FIG. 40A.

Referring now to FIG. 41A, a range aggregation of column information isillustrated, applying for convenience the same table illustrated in FIG.40A. The aggregation criteria applied to column B in FIG. 41 A, ratherthen selecting single cell values, selects a range of column cell valuesand aggregates the data associated with the rows grouped by the selectedcriteria. For example, aggregating a column B in FIG. 41A using a rangeof 250, for example, as illustrated, using a base level of 0, willresult in a table 4120 as shown in FIG. 41B. Applying an averagingfunction to the underlying data in column C, in FIG. 41B, results in theillustrated table 4130 of FIG. 41C.

The parameters for parameterized aggregation can be automaticallypresented based on raw column type (such as string, numeric, date), thesemantics of that column (for example—column name), the view, and theuser's previously selected parameters for that column.

In operation, referring to FIG. 40 or FIG. 41, the user initiates theaggregation operation by clicking on the ‘{’ control. The system, if soconfigured, can perform, for example, in response to single action, animmediate default aggregation (for example a basic aggregation, or theaggregation performed last time). If a parameterized aggregation isperformed in a non default mode, the system displays an aggregationcontrol panel 5010 in any of a number of convenient display formats, forexample a pop up window, or in a designated area appearing above thetable, as shown in FIG. 50. Deselecting column aggregation, will removecolumn aggregation panel, if it was displayed.

In the aggregation control panel display, aggregation criteria will bepresented and will be context sensitive (either one or a combination ofper column data type, column semantics, per view, per user). Forexample, if the aggregated column represents dates, and parameterizedaggregation is selected, the displayed criteria could present a choiceof aggregating the data by week, month, quarter, year or anotherincrement to be used for aggregation (for example, aggregate by eachconsecutive 3 days). In the case of text columns in a parameterizedaggregation, the displayed criteria could be a choice of regularexpressions. In addition, the context sensitive history of a user'sprevious selections can be displayed. That history is dependent at leaston the column and/or the aggregation type selected. The user can chooseadditional aggregation parameters from the aggregation control panel.Upon selection, a table corresponding, for example, to FIG. 40B or 41B,is presented for view.

Filtering

Referring to FIGS. 42A-C, in addition to the controls already described,another column control ‘*’ 4201 is used for dynamic filtering of thetable by the content of selected column. The table rows can bedynamically filtered by any column or columns in the table. A column isselected for filtering by activating the ‘*’ filtering control, and willbe visually marked (for example an enlarged or highlighted ‘*’ 4202) toindicate the selection. In the newly created filtered table 4220, onlythe rows that match the filter criteria in the filtered column orcolumns will be displayed. As a result, the totals in the columns, wheretotals are computed, can be affected. The effect of column filteringwill be reversed after deselecting the selected ‘*’ control in thecolumn, and the visual marking of previously selected control 4202 willbe removed. In the case where the table is already aggregated, the rowsof the table underlying the aggregated table are those that filtered.

For example, in FIG. 42A filtering is applied to column B by selectingcontrol button ‘*’ 4201 in that column. As illustrated in FIG. 51A, afilter control panel 5110 appears, for example as a pop-up window ordisplayed above the table. The user sets the filter criteria for thatcolumn, for example, a range between 300 and 900 (as shown in FIG. 51A,the filter control panel 5110 at this point presents filter criteria5115 for column B) and applies it. As a result, a new table 4220, asshown in FIG. 42B, is displayed. Subsequently, activating a filtercontrol in a different column will display new filter criteria in thefilter control panel 5120 for each column to be filtered. Setting thefilter in the range between 100 and 300 in column D (as shown in FIG.51B, a filter control panel 5120 at this point presents filter criteria5115 for column B and filter criteria 5215 for column D) results in thetable 4230 as shown in FIG. 42C.

Filter criteria presented in the control panel will be context sensitive(either one or a combination of column data type, column semantics (forexample—column name), view and user history). For example, if thefiltered column represents dates, the criteria presented could be achoice of start date and end date, or criteria including only rows whosedate is within a specified number of date units (for example, filterfrom today going forward a week). In the case of text columns, thefilter criteria could present a choice of regular expressions. Uponactivating a filter in the filter control panel, the selected filtercriteria will be applied to the table. In addition, the contextsensitive history of a user's previous selections can be displayed. Thathistory is dependent on the column to which the filtering is applied.The user can choose additional parameters from the filtering controlpanel. In both cases of aggregation and filtering, the user can bevisually presented with indications as to the nature of the informationpresented. For example, the title of the view will indicate if the viewis aggregated and/or filtered and will provide the correspondingdetails.

Charting

Referring again to FIGS. 18 and 19, the column header can also have acontrol button “o” 650 (FIG. 18) to indicate charting. Clicking on thisbutton, will cause the system to present a graph/chart 656 (FIG. 19) forthe selected column. The column is visually marked in the column headerby having a larger “O” button 654 (FIG. 19). Clicking on the “O” button654 will deselect the charted column reverting control button “O” to itsoriginal size and will close the display chart/graph for this column.

Charting/graphing can be enabled for one column at a time, or formultiple columns (either real columns or proxy columns). A proxy columnis one not fully revealed in the selected, displayed column. In the caseof uni-column charting/graphing control, selecting the control willresult in displaying one chart/graph at a time for the associated table.In the case of multiple column charting/graphing, the system willdisplay a chart/graph of each of the plural selected columns separately,or combine them in one chart/graph, if possible, depending for example,on data and/or chart/graph type. Each of the charts has separatecontrols for further customization, for example a chart type control658.

For example, referring to FIG. 45A, charting/graphing is applied tocolumn B by selecting control ‘o’ 4501 in that column of table 4510. Asa result, a chart 4525 is displayed together with a table 4510, wherechart/graph control 4502 is visually marked, as shown in FIG. 45B. Ifcharting/graphing is set for uni-column operation, then selectingcharting/graphing control 4503 in column D in FIG. 45B, will result asshown in FIG. 45C, in a table 4510, where chart/graph for column B isreplaced by chart/graph 4535, where control 4504 is visually marked, andthe visual marking of control 4501 is removed.

If charting/graphing is set, by the user or system, for multi-columnoperation with a separate chart/graph display for each column, thenselecting charting/graphing control 4503 in column D in FIG. 45B, willresult, as shown in FIG. 45D, in a table 4510, where both control 4502and control 4504 are visually marked, and chart/graph 4535 is displayedalong with chart/graph 4525. Further clicking on control 4502 in columnB in FIG. 45D will deselect the chart/graph for that column, and willresult, as shown in FIG. 45E, in a table 4510 where the visual markingis removed from control 4501, and only graph/chart 4535 is displayed.

If charting/graphing is set for multi-column operation, where the datais combined in one chart/graph, then selecting charting/graphing control4503 in column D in FIG. 45B, will result, as shown in FIG. 45F, intable 4510, where both chart/graph controls 4502 and 4504 are visuallymarked, and a combined chart/graph 4565 for displaying the data of bothcolumns B and D.

Shown in FIG. 45G, are table 4510, the combined chart 4565 of columns Band D, visually marked chart/graph controls 4502 and 4504, a controlpanel 4590 for the table, and chart/graph “undo” column control 4592 forthe table. Selecting control 4592 in FIG. 45G, results, as shown in FIG.45H, in table 4510 without removing chart/graph 4565, and with thevisual marking from controls 4591, 4501 and 4503 removed. If, control4591 in FIG. 45H is selected, it will result in displaying the combinedchart/graph for columns B and D (the “undoing” of the last operation) asshown in FIG. 45G. In the case where table data is continuously updated,(for example, using the adaptive pull mechanism in the case of an HTMLbased application) the associated charts/graphs are updated accordingly.

The appropriate graph/chart type can be automatically chosen based onthe view, the column and the data, if the system is set up for automaticselection. For example, if the data is negative, a horizontal bar graphcan be used, and if the view is an aggregated view, a pie chart can bedisplayed. Otherwise, the system will present the default or mostrecently used chart/graph type, and provide the capability to selectfrom other chart types, as shown for example, in FIG. 19, chart 656.

The invention also provides a view column control follow-up feature,which allows for the relevant column control information and relatedpresentation to propagate from one view to another view, such as, forexample, propagating from aggregate view to detail view, or propagatingamong different views in the same view group.

The view column control follow-up can be provided for both multi-columnand uni-column controls, as long as the data in the followed-up view canbe presented in a non-conflicting manner. For example, a column sortlock and column charts that are presented in aggregated view can beautomatically presented in a detail view. (For an aggregated view, whichhas presented chart/graphs, the drill down can be performed using achart/graph or using folder-like control 4003A in aggregated rows in thetable). As a result, the detailed view will be sorted in the same orderas aggregated view, and charts presented in the aggregate view will bepresented in detail view.

Similarly, all the described controls in the columns can be applied tothe rows as well, in which case full symmetry is applied where rows willbe substituted by columns, and vice versa. The table, if appropriate,will have a selection mechanism to decide if it is column controlled oralternatively row controlled.

A table, according to the invention, has the capability of dynamicallyadding columns from an available database of virtual columns or removingcolumns from the table. That capability, combined with dynamicaggregation by any column and filtering by any column combination (thatis, by more than one column) provides a very flexible method for datasearching and presentation.

A table's columns can thus be of two types: regular and virtual. Regularcolumns are ones that appear in the tables, either visible or not(hidden). The virtual columns are ones that can be added to the table,either as a regular column or a proxy column. A proxy column is a columnto whose content, column manipulation can be applied, therebypotentially changing the displayed data in the table or in a viewrelated to the table, but without displaying the actual data of theproxy column. A virtual column can be selected from the virtual databaseusing a list, a browsing mechanism or another convenient method. Theuser can decide how to use the virtual column (either as real or proxycolumn).

A preferred embodiment, according to this aspect of the invention, for aproxy column features a column header for a regular column, whichcontains all the column controls. Furthermore, the selected column canbe instantiated as a new column in the table. In addition, the list ofcolumns can be provided dynamically, based on available databaseinformation and may be presented as a combination of column type, columnsemantics and user preferences. Further, if a column can beparameterized, appropriate parameter choices for instantiated columnwill be provided. Referring to FIG. 49, for example, if the column isP&L (profit and loss), choices of time horizon will be provided, such asdaily, weekly, monthly, quarterly and yearly, as well as potentially anoptional parameter, if it is realized or unrealized.

For example, a proxy column can be sorted upon, potentially changing theorder of the table rows; or a proxy column can be charted withoutaffecting the display of the table. As an example, in FIG. 43A, a table4310 and a virtual column database 4315 are illustrated. Selecting acolumn M from the database 4315 and adding it to the table 4310 resultsin table 4320, as shown in FIG. 43B, with column M being added to thetable as regular column.

All displayed regular columns can become virtual. FIG. 43C illustrates atable 4330 with a ‘V’ control 4332 in the table headers, which were forexample activated by using control actuation button 600. Activating the‘V’ control in column C will remove this column from the table 4330,resulting in table 4340 as shown in FIG. 43D, although the column isstill available for all purpose in the virtual column database 4315. Theuse of the virtual columns is illustrated in FIGS. 43E-I. The column Mis added, as a result of user selection, as a proxy column to the table4350 (FIG. 43E) from the virtual column database 4315. The resultingtable 4360 is shown in FIG. 43F, where 4365 represents a proxy column M.(Note that the content of the proxy column is not displayed, whereas thecontent is displayed when the virtual column is selected as real column,and therefore added to a table, as in FIG. 43B.) Sorting table 4360 byascending value content of column M (which has values of 125 for row 1,175 for row 2, and 100 for row 3 as shown in column content 4366) byactivating a sort ascending control 4367 in the proxy column headerresults in the table 4370 shown in FIG. 43G, where control 4367A isvisually marked.

Activating a graph control 4368 in proxy column 4365 in a table 4360results in table 4380, where control 4368A is visually marked and graph4385 is shown in FIG. 43H. Activating an ‘R’ control 4369 in proxycolumn 4365 in table 4360 will make the column a regular column M intable 4390, as illustrated in FIG. 43I.

Override Feature (Cell Operation)

Referring to FIG. 4, and the flow chart of FIG. 52, in another aspect ofthe invention, a display of a so-called “override” is presented intabular form 74. In accordance with this aspect of the invention, thesystem, for example, but not necessarily, in real time, provides foroverriding the data provided by the system with user-generated data.Accordingly, referring to FIG. 4, the tabular representation 74 includesa so-called “override” section illustratively shown as the last columnunder “local price.” (Other columns could be identified as“overrideable” as well, provided, in accordance with the system, theirdata can be overwritten.) In this section, the user selects the cell(s)to override (step 5210) and can enter price data (step 5220), which isto override the actual price provided by the data in the system 18. Inoperation, the view may present, for a cell, a display of a text field77 a and an override button 76 (x). Upon “clicking” on the overridebutton “x,” (at step 5225) after entering the override data in the textfield (here 25), the user's system will forward the override datathrough the network (step 5230), for example the web, to the system 18where it will be used to recalculate all of the other dependent data inthe system (step 5235) either locally or globally as determined by theuser system. A new page display will then be generated (step 5240)containing an added unoverride button 77 in the cell being overridden,and provided to the user for display by the web server 40 (step 5250).(Each of the users that will have access to the effects of theoverridden data, will see the changes according to system operation.) Inthis configuration, the user can thereafter “unoverride” the overriddendata (step 5260) by clicking on the unoverride button 77 (whichconditionally appears only in an overridden cell) and the system 18 willthen reverse the overridden data with associated system provided data ifsuch data exists, and will recalculate all of the data with such systemprovided data. The resulting revised display will then reflect thesystem provided value for any of the data, which has been “unoverrode.”Further, it is important to recognize that the system provided data maybe dynamically changing or at least updated from the time of theoverride.

Accordingly, the system thus provides an operational flexibilityunavailable previously and enables the real-time data presentation to beoverridden in any and all of the processed displays presented by thesystem, and then “unoverridden”.

Row Operations

While the description herein has concentrated upon column manipulationsand activities, as noted above, the same tools and functions could beequally applied to rows of a table. Further, however, the user has acapability in accordance with the invention to select a row, forexample, by selecting a symbol, and to indicate for the selected rowvarious operations similar to, but different than, those describedabove. Referring now to FIG. 8A, in one aspect, a user can modify oredit some of the row information by displaying the original screen wherethe row is defined, and effecting the modification. For example, a tradecan be modified by clicking on the “Modify trade” control button 800.This causes a new screen to open (FIG. 8B), and the user either modifies802, or cancels the trade, 803, causing a new window to open. After theuser confirms that the trade is to be modified by clicking on the “yes”button 900 (FIG. 9), the system displays, referring to FIG. 10, thedetailed data for that selected trade entry. The user can modify thistrade entry as desired, and when done, the modified trade will replacethe original trade in the user display (FIG. 8A) as well as in thesystem 18 storage and memory.

In another aspect of the invention, the user can require and display,for portfolio analysis, aggregated data (as described above) collectedby any of a variety of characteristics, for example, by country asillustrated in FIG. 11. Alternative aggregated views can be provided topresent the data, as noted in line 1000, by allocation, by asset class,by currency, by industry etc. These views, while accessed by the user,will be kept in the ViewServer cache 70 for display by theApplicationServer 42 through the web server 40. When the aggregatedsymbol is clicked upon, a more detailed presentation, as shown in thedisplay detail drill down table of FIG. 12, will be displayed.

Adaptive Pull

In accordance with another aspect of the invention, as noted above, themetadata is preferably provided with the retimed web page toautomatically refresh the display at a periodic rate. When a refresh isrequested by the browser, at 200, referring to FIG. 8, theApplicationServer 42 inquires of the system, at 202, whether any of thedata and/or presentation has changed, and if any has changed, thatupdate data is available at 204 in ViewServer cache 70. Cache 70 isconstantly being updated, asynchronously, as new data is acquired by thesystem, or as data is rearranged. The page is then reassembled andpassed through the ApplicationServer at 206, to the web server at 208,and then to the user browser for eventual display at 210. This is asimple process for “HTML” pages.

If no change has been made in the data and/or presentation, then thereis no need to provide a further update and the same page can be used at209.

The system can automatically provide for a dynamically changingrepetition rate for the refresh depending upon parameters set inaccordance with the system operation. Thus, refresh can occur much morequickly when changes have been requested to be made to the display atthe user system, but updates can be made much less frequently when, forexample, further user requests have not taken place, for example, forten minutes, or when the markets have closed. Other use parameters canalso be provided to control the rate of refresh of the display, such astabular display 72. For the financial markets, this can be depend uponthe instruments being displayed, the time of day, the nature of themarket, whether this is a new view or a new page (the system willautomatically display a default view of the page when entered the firsttime), etc.

Alternative Data Sources

The ViewTOTAL data sources and processing servers are dependent on thetask at hand and can vary. One useful embodiment is to load a table (ortable like data) into ViewTOTAL from an external data source, forexample, a spreadsheet, and allow it to be manipulated through controlsprovided in the interactive table described above. It can also share theresulting interaction with other users in the network. Another usefulinteraction is to load information into ViewServer from the web page byparsing it. The resulting information can be presented separately of theoriginal page, or it may be displayed within a page which emulates theoriginal page where a new table is substituted by the interactive table.

For example, the system can parse data from a data source (for example,a file, a database, a web page, etc.) and load it in ViewTOTAL forfurther interaction and sharing. Referring to FIG. 48, the system isprovided, manually or automatically, with a data source (step 4810). Ifthe data source is a web page address (URL), tested at 4820, the systemparses the page and extracts table or table-like information from thepage (step 4830). The system also maintains the original pageinformation for further possible page duplication (step 4840). If thedata source was not a web page address, the system extracts the dataform the non web page data sources at 4845. If no errors occur, testedat 4850, the system attempts to analyze and classify the data at 4855.One example of the results of the system analysis is to identify a datacolumn type.

The results of the analysis can them be presented to the user forcorrection or augmentation (step 4860). The system then loads theextracted table data information into the ViewTOTAL through theDataServer, populating other servers, for example ViewServer and theAnalyticalServer, caches. This is indicated at 4865. The ViewServermaintains the information in a table format (step 4870), and theApplicationServer constructs a new page with a new table havinginteractive controls and populates the new table with the table from theViewServer (step 4875). The system then presents the new page which willcontain the new interactive table, where, in the case of a web page datasource, it can, if requested, provide a duplicate of the original pageto the extent possible, where the original table is replaced with thenew interactive table (step 4880). In a particular aspect of theinvention, the new page can contain a link to the original page (step4885).

The user can then interact with the new table through its controls whichcommunicate with the ViewServer (through the web server and ApplicationServer as described above) (step 4890). The ViewServer responds to theuser interaction as described hereinbefore and manipulates the tableaccordingly (step 4892). The ApplicationServer can construct the pagecontaining a pre-arranged table which load information from theViewServer cache and returns the page to the user through the web server(step 4894). The new page can be further shared among other users usingthe system sharing infrastructure as described in more detail elsewhere(step 4896). Finally, a new table cam be saved at any point of theinteraction with the user in the system or at the user location for yetfurther interaction (step 4898).

Client-Based Programs

In an alternate embodiment of the invention, client-based programs (suchas Java applets, C# programs, or local programs) can be employed todownload, through the web, the necessary information, preferably on areal-time basis, to update the user view. In this aspect of theinvention, the client-based programs are created so that most of theprogram effort takes place at the servers of system 18 while arelatively “thin” program is downloaded to the user's browser, ordeployed on the user's computing devices. The refresh of data at theuser display takes place, incrementally and dynamically, preferably inreal time. The client-based program reads the display configuration fromthe server and dynamically creates appropriate view groups. One programcan flexibly present any view groups, and any views within a view group,as well as any columns in the case of a table based configuration.Preferably, the user display changes occur in a minimum number ofelements such as, in the case of tables, symbols, fields and cells asopposed to full pages in the case of HTML. Symbols (and hence rows) andfields (and hence columns) can be dynamically added and deleted as wellas cells being dynamically updated. The program can deal with visualrepresentation and interaction without necessarily fully “understanding”the content meaning.

Thus, according to this aspect of the invention, it is only necessary touse the “thin” client-based program since in this embodiment much of theavailable information or data is handled at the server. This results ina real time dynamic update of the information on display at the user'ssite.

One Click Failover

In yet another aspect of the invention, the display includes a “failoverbutton”, which can be used in those instances where, for some reason,the system 18 is unable (or is slow, for example) to provide the displayupdates. In this embodiment of the invention, referring to FIGS. 5A and5B, clicking on the failover button enables the system to access analternate web server 40 b connected to communication private networks30, 32 to access an alternate ApplicationServer 42 b. The alternateApplicationServer 42 b, as illustrated in FIG. 5B, then accesses theoriginal ViewServer for the user, which maintained the display viewparameters previously used to create the display seen by the user, anddelivers it to the user browser, for example, through a faster route. Ifthe original ViewServer were also unavailable, an alternate server wouldpick up the views recently accessed by this user. The ApplicationServeris thus able to update the previous display view, which is cached at theViewServer, and delivers it through the web server 40 b, to the Internetand then to the user, thus enabling a reliable and redundant connectionto the data even if, for example, the web server 40 a and/orApplicationServer 42 a, originally being employed, were to fail or slowdown. This operation is illustrated in FIG. 5A, the “before failovermode” configuration and FIG. 5B the “after failover mode” configuration.Importantly, it is the user who, in this embodiment, initiates thetransfer upon recognizing the inability to obtain further updates orother views from the system 18 using the path originally assigned to it.

The link to the failover server will be generated by the currentApplicationServer with the name of the failover server, with anencrypted user identification (such as an access identifier or user nameand password), timestamp (if the button is pressed after certain timeperiod it will not be allowed to login for security reasons) as well asother parameters such as view name. The failover server will log in theuser, connect to the ViewServer and display the specified view and assuch it will provide “hot recovery.” Thus, for example, before failover,a page can have associated with it “failover” buttons (and written inthe pages) as follows:

Button1 Button2 FailoverButton [http://serverA . . .] [http://serverA .. .] . . . [http://serverB . . .]

-   -   After failover, the displayed page can contain the alternate        failover identifications:

Button1 Button2 FailoverButton [http://serverB . . .] [http://serverB .. .] . . . [http://serverA . . .] or Button1 Button2 FailoverButton[http://serverB . . .] [http://serverB . . .] . . . [http://serverC . ..]

-   -   if more than 2 web servers are available for further redundancy.        General Look and Feel

Referring to FIG. 6, at the user/browser site, many different typedisplays can and are provided by the system 18. As noted above, inconnection with FIGS. 3 and 4, various tables 80 can be provided toillustrate the data being requested. But in addition, graphs 82, charts84, news text 86 and various Alert information, either in the formtables, texts, graphs, charts, or other indicia, can be provided anddisplayed to the user. In particular, when using, for example, thetables provided in FIG. 3, color can be indicative of changes in valuefrom a previous update, or from an update within the previous, forexample, ten minutes. Thus, red can, for example, be used to indicatevalues in any cell that have decreased in value while green might beused to represent values that have increased in value. This easy visualindication of changes in various portions of the table provide the userwith an immediate advantageous secondary source of visual indication toenable quick understanding and mental analysis of the display beingpresented. This is particularly useful where the display is bothinvolved and complex.

Referring to FIG. 6, each of the graphs, charts, and otherpresentations, etc. have a defined configuration. In accordance with apreferred embodiment of the invention, each user has his own preferredconfiguration for the graphs, tables, etc. The server maintains theconfiguration information for the user and provides to the user theinformation as the user has previously designated. In addition, asillustrated in, for example, FIG. 3, many of the applicationpresentations have a structure in which they provide a View Group 800such as the group's portfolio, trades, markets, trade entry, and log out(FIG. 3), and within the View Groups, views which include theinteractive views 60.

The ViewServer will keep configuration data on a per user basis,identifying what View Groups 800 and Views 60 the user sees, as well asparameters for Tables (for example, which column to show and in whatorder) and Charts (for example, a default chart type). By clicking onUser View Group, the application shows a list of Views for this group.By Clicking on the View, the application shows the presented data on oneor more tables or charts or on a combination of them. Note also thatcertain views, like tables and charts, typically display dynamicallychanging information.

Referring to FIGS. 20A-D each page will have different display areassuch as Display Browse Controls (View Group controls, View controls,View Slice controls), TableView, ChartView, AlertView, NewsView,MessageView etc. Each of those and other display areas can be hidden orrevealed by display area control actuation buttons, such as buttons1800, 1801, 1802. Selecting such a control button on the visible areawill make this area disappear. Selecting it again will make this areareappear. Selecting button 1800 in FIG. 20A will cause the page view tochange and look like FIG. 20B. Selecting button 1802 in FIG. 20B willcause the page view to change and look like FIG. 20C Selecting button1802 in FIG. 20C will cause page view to change and look like FIG. 20D(the same view as FIG. 20B).

As noted above, to display data updates on the user screen, theViewServer will refresh the page using the “refresh” meta tag embeddedin the page HTML. The direction of the data change in the datapreferably is provided by a color change, for example green to indicatean increase in value and red to indicate the decrease in value.

The user will have an interface to create new views from virtualcolumns. In addition the user can specify, other attributes such asfilters, aggregations, e.t.c. At any point of time the view can bereconfigured, named and saved with its attributes. Also, the user willhave an interface to create a ViewGroup and add/remove views, name andsave ViewGroups, as well as create application displays by choosingViewGroups. As such, the user has a full interactive capability tocreate his own configurable applications, which can be reconfiguredfurther later.

In the foregoing specification, the invention has been described withreference to specific embodiments thereof. It will, however, be evidentthat various modifications and changes may be made thereto withoutdeparting from the broader spirit and scope of the invention. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

Additions, subtractions, and modifications of the disclosed preferredembodiments of the invention will be apparent to those of skill in thisfield and are within the scope of the following claims.

The invention claimed is:
 1. A method for sharing content, the methodcomprising: generating, for a first user, within a system, content forone or more application displays to be displayed on a first computingdevice of the first user; sending, to at least one second computingdevice of at least one second user, a first message to share sharablecontent; wherein the at least one second user includes a plurality ofsecond users; wherein the sharable content includes at least a portionof content from the one or more application displays that were generatedfor the first user; wherein the first message includes an accessidentifier that provides access to the sharable content; wherein the atleast one second computing device is different from said first computingdevice of the first user; in response to receiving an indication ofacceptance of the first message by a particular second user, of theplurality of second users, the system using the access identifier toshare with the particular second user said sharable content; the systemusing the access identifier to determine which content within the systemto share with the particular second user; prior to sending the firstmessage, enabling a plurality of users to share the sharable content;enabling each user, in a set of users, to interact with at least oneapplication, from one or more applications that are associated with thesystem, through at least one application display from a plurality ofapplication displays; wherein the plurality of application displays areassociated with the system; wherein the plurality of applicationdisplays include the one or more application displays; wherein theplurality of application displays include a plurality of views; whereinthe plurality of users belong to the set of users; wherein the firstuser and the at least one second user belong to the set of users;monitoring, by the system, for occurrence of events from a plurality ofevents; wherein each event, from the plurality of events, corresponds toat least one of: a) interaction with the system, by at least one userfrom the set of users; or b) at least one information update to contentof at least one view from the plurality of views; wherein the firstmessage is a first alert that was automatically sent in response to afirst event, from the plurality of events; wherein the first event is anevent from the plurality of events that corresponds to an informationupdate to the sharable content; causing display of the first alert in arespective application display, from the plurality of applicationdisplays, of each of the plurality of second users; wherein therespective application display of each of the plurality of second usersincludes at least one other alert, which is concurrently displayed withthe first alert in the respective application display, about a differentevent from the plurality of events; enabling each user, of the pluralityof second users, to enter one or more comments in relation to the firstalert and to share said one or more comments, among the plurality ofsecond users, in relation to the first alert; receiving, by the system,a comment, entered in a text entry interface that is related to thefirst alert, from the particular second user ; causing display of thecomment, in relation to the first alert, to each user from the pluralityof second users; and wherein the first alert was sent to the particularsecond user based on receiving from the particular second user, by thesystem prior to the first event, an expression of interest in beingnotified about information updates to the sharable content.
 2. Themethod of claim 1 wherein: the sharable content is associated with aparticular data set; the particular data set includes a plurality offields; the method further comprises enabling updates to one or morefields, from the plurality of fields, by authorized users from the setof users; the particular data set is maintained in a database in thesystem; and the first event corresponds to an update to at least onefield from the one or more fields.
 3. The method of claim 2 wherein theupdate to the at least one field is performed by a user.
 4. The methodof claim 2 wherein the particular data set corresponds to a transaction.5. The method of claim 4 wherein said transaction is a transactioninvolving an item.
 6. The method of claim 5 wherein said item is afinancial instrument.
 7. The method of claim 1 wherein the accessidentifier is a URL.
 8. The method of claim 1 wherein: within therespective application display of a user, from the plurality of secondusers, the at least one other alert is a plurality of other alerts; afirst other alert and a second other alert belong to the plurality ofother alerts; the first other alert is an alert about a second event,from the plurality of events, that corresponds to a second informationupdate to the sharable content; and the second other alert is an alertabout a third event, from the plurality of events, that corresponds to athird information update to content of a particular view from theplurality of views.
 9. The method of claim 1 wherein receiving theexpression of interest comprises receiving a specification of interestin being notified about information updates to the sharable content. 10.The method of claim 1 further comprising: in response, at least in part,to occurrence of a second event, of the plurality of events, associatedwith interaction with an application, of the one or more applications,by a particular user of the set of users, sending a second alert to eachuser of a plurality of third users, from the set of users, about thesecond event, to cause display of the second alert in a respectiveapplication display, from the plurality of application displays, of eachof the plurality of third users; wherein the second alert includes asecond access identifier that provide access to one or more views thatare associated with the second event; wherein the plurality of thirdusers is different from the plurality of second users; wherein theparticular second user belongs to the plurality of third users;receiving, by the system, a second comment, entered in a text entryinterface that is related to the second alert, from the particularsecond user; causing display of the second comment, in relation to thesecond alert, to each user from the plurality of third users; whereincausing display of the comment includes causing the comment to bedisplayed, in relation to the first alert, in the respective applicationdisplay of the particular second user; and wherein causing display ofthe second comment includes causing the second comment to be displayed,in relation to the second alert, in the respective application displayof the particular second user.
 11. The method of claim 10 wherein theapplication is a financial application.
 12. The method of claim 10wherein the application is associated with the system at least in thatthe system enables the particular user, at least in part, to interactwith at least a portion of content of the application.
 13. The method ofclaim 12 wherein the application is provided by the system.
 14. Themethod of claim 10 wherein sending the second alert to at least onethird user, of the plurality of third users, is performed based onreceiving from the at least one third user, by the system prior to thesecond event, a specification of interest in being notified aboutinteractions of the particular user.
 15. The method of claim 10 wherein:the second event corresponds to input of a text, by the particular user,into a text entry interface that is related to a given view that isshared at least in part among the particular user and the plurality ofthird users; the method further comprises maintaining at least a portionof content of the given view by the system; and the second accessidentifier provides access to said given view.
 16. The method of claim 1wherein the text entry interface is a text view.
 17. The method of claim10 wherein: the second event corresponds to the particular user loadingat least a portion of a file to the system; and the second accessidentifier provides access to the at least a portion of the file. 18.The method of claim 17 wherein the second event corresponds to theparticular user loading at least one table from the file.
 19. The methodof claim 10 wherein: receiving the expression of interest comprisesreceiving a specification of interest in being notified aboutinformation updates to the sharable content; and sending the secondalert to the plurality of third users includes sending the second alertto the particular second user based on receiving from the particularsecond user, by the system prior to the second event, a specification ofinterest in being notified about interactions of the particular user.20. The method of claim 19 wherein: the second event corresponds to theparticular user loading at least a portion of a file to the system; thesecond access identifier provides access to the at least a portion ofthe file; the sharable content is associated with a particular data set;the particular data set includes a plurality of fields; one or morefields from the plurality of fields are updateable by authorized usersfrom the set of users; the particular data set is maintained in adatabase in the system; the particular data set corresponds to atransaction; and the first event corresponds to an update to at leastone field from the one or more fields.
 21. The method of claim 1 whereinthe information update was performed by the first user.
 22. The methodof claim 1 wherein the information update was performed by the systemwithout receiving input from any user.
 23. The method of claim 22wherein the information update was performed by the system in responseto receiving information from a data source that is external to thesystem.
 24. The method of claim 23 wherein the data source is a datafeed.
 25. The method of claim 1 wherein: the respective applicationdisplay of at least one user, of the plurality of second users, isassociated with the system at least in that content of the respectiveapplication display of the at least one user, of the plurality of secondusers, includes content obtained from the system; and said contentobtained from the system includes the first alert and the at least oneother alert.
 26. The method of claim 1 wherein acceptance of the firstmessage includes usage of the access identifier by the particular seconduser.
 27. The method of claim 1 wherein the sharable content is at leastone view from the plurality of views.
 28. The method of claim 1 whereina particular application display of the one or more application displaysincludes at least two views; and the sharable content includes at leastone but not all of the at least two views.
 29. The method of claim 15further comprising: maintaining said sharable content, by the system, inat least one database; and wherein the information update corresponds toan update to database information, that corresponds to the sharablecontent, in the at least one database.
 30. The method of claim 29wherein the sharable content includes a table view; and said updateddatabase information corresponds to at least cell in the table view thatwas updated by the information update.
 31. The method of claim 1,wherein the sharable content includes content from one or more tableviews, and the information update includes an update to the one or moretable views.
 32. The method of claim 1, wherein the sharable contentincludes content from one or more chart views, and the informationupdate includes an update to the one or more chart views.
 33. The methodof claim 1, wherein the sharable content includes content from one ormore alert views, and the information update includes an update to theone or more alert views.
 34. The method of claim 1, wherein the sharablecontent includes content from one or more of news views, and theinformation update includes an update to the one or more news views. 35.The method of claim 1, wherein the sharable content includes contentfrom one or more of message views, and the information update includesan update to the one or more message views.
 36. The method of claim 1wherein the sharable content contains, at least in part, financialinformation.
 37. The method of claim 1 wherein the sharable contentcontains, at least in part, dynamically updated information.
 38. Themethod of claim 1 further comprising, in response to a secondinformation update to the sharable content, sending the secondinformation update, in real-time, to the plurality of second users. 39.The method of claim 9 wherein receiving the specification of interestcomprises receiving a specification of interest in a particular view.40. The method of 39 wherein receiving the specification of interest inthe particular view includes specification of at least one condition,that is associated with the particular view, to be monitored.
 41. Themethod of claim 40 further comprising, providing, by the system, in thefirst alert, a description of change in the at least one condition. 42.The method of claim 10 further comprising, causing display of at leastone update, in real-time, in the one or more views.
 43. The method ofclaim 1 wherein the information update was caused by recalculation ofnumeric content that is associated with the sharable content.
 44. Themethod of claim 1 wherein the step of causing display of the commentcomprises causing display of the comment, in real-time, to each userfrom the plurality of second users.
 45. The method of claim 1 whereinthe step of sending the first message comprises sending the firstmessage to a given second user, of the plurality of second users, basedon receiving by the system prior to the first event, from the particularsecond user, a request to notify the given second user about informationupdates to the sharable content, wherein the given second user is adifferent user than the particular second user.
 46. A system, comprisingone or more processors configured to execute instructions that cause thesystem to perform a method comprising steps of: providing acomputer-based service over a network to a set of users, wherein a firstuser and a second user belong to the set of users; receiving, by thecomputer-based service from the first user, a first specification ofinterest in being notified about information updates to firstinformation; receiving, by the computer-based service from the seconduser, a second specification of interest in being notified aboutinformation updates to the first information; receiving, by thecomputer-based service from the first user, a third specification ofinterest in being notified about information updates to secondinformation; wherein the second information is different from the firstinformation; after receiving the first specification, the secondspecification and the third specification, in response, at least inpart, to at least one information update to the second information, thecomputer-based service performing the step of: without sending thirdinformation to the second user, sending the third information to thefirst user based, at least in part, on the third specification, to causedisplay of the third information in a first application display of thefirst user; after receiving the first specification, the secondspecification and the third specification, in response, at least inpart, to at least one information update to the first information, thecomputer-based service performing the steps of: while the firstapplication display includes the third information, sending fourthinformation to the first user, based, at least in part, on the firstspecification, to cause display of the fourth information in the firstapplication display concurrently with the third information; based, atleast in part, on the second specification of interest, sending thefourth information to the second user to cause display of the fourthinformation in a second application display of the second user, whereinthe second application display does not include the third information;and wherein the fourth information includes a first access identifierthat provides access to the first information; in response, at least inpart, to receiving, by the computer-based service from the first user, afirst comment entered in a first text entry interface that is related tothe fourth information, the computer-based service sending the firstcomment to the second user; and causing display of the first comment, inthe second application display, in relation to the fourth information.47. The system of claim 46 wherein the method further comprises limitingaccess to the first comment to users in the set of users who areauthorized to access the fourth information.
 48. The system of claim 46wherein the method further comprises: causing display of the firstcomment, in the first application display, in relation to the fourthinformation; in response, at least in part, to receiving, by thecomputer-based service from the second user, a second comment, enteredin a second text entry interface that is related to the fourthinformation, the computer-based service sending the second comment tothe first user; and causing display of the second comment, in the firstapplication display, in relation to the fourth information and the firstcomment.
 49. The system of claim 46 wherein the third informationincludes a description of the at least one information update to thesecond information and a second access identifier that provides accessto the second information.
 50. The system of claim 46 wherein the stepof causing display of the first comment is performed in response, atleast in part, to receiving, by the computer-based service from thefirst user, the first comment.
 51. The system of claim 46 wherein themethod further comprises maintaining, by the computer-based service, thefirst information.
 52. A method comprising: providing a computer-basedservice over a network to a set of users, wherein a first user and asecond user belong to the set of users; receiving, by the computer-basedservice from the first user, a first specification of interest in beingnotified about information updates to particular information; receiving,by the computer-based service from the second user, a secondspecification of interest in being notified about information updates tothe particular information; receiving, by the computer-based servicefrom the first user, a third specification of interest in being notifiedabout information updates to given information; wherein the giveninformation is different from the particular information; afterreceiving the first specification, the second specification and thethird specification, in response, at least in part, to at least oneinformation update to the given information, the computer-based serviceperforming the step of: without sending first information to the seconduser, sending the first information to the first user based, at least inpart, on the third specification, to cause display of the firstinformation in a first application display of the first user, whereinthe first information includes a given link that provides access to thegiven information; after receiving the first specification, the secondspecification and the third specification, in response, at least inpart, to at least one information update to the particular information,the computer-based service performing the steps of: while the firstapplication display includes the first information, sending secondinformation to the first user, based, at least in part, on the firstspecification, to cause display of the second information in the firstapplication display concurrently with the first information; based, atleast in part, on the second specification of interest, sending thesecond information to the second user to cause display of the secondinformation in a second application display of the second user, whereinthe second application display does not include the first information;and wherein the second information includes a particular link thatprovides access to the particular information; in response, at least inpart, to receiving, by the computer-based service from the first user, afirst comment entered in a first text entry interface that is related tothe second information, the computer-based service sending the firstcomment to the second user; and causing display of the first comment, inthe second application display, in relation to the second information.53. The method of claim 52 wherein the particular information isinformation that is maintained, by the computer-based service, for aparticular application display.
 54. The method of claim 52 wherein theparticular information is information that is maintained, by thecomputer-based service, for at least one view.
 55. The method of claim52 wherein the computer-based service sending the first comment to thesecond user without resending the second information to the second user.56. The method of claim 52 wherein the computer-based service sendingthe first comment to the second user without receiving from the firstuser any explicit indication of to whom to send the first comment. 57.The method claim 52 wherein the first text entry interface is related tothe second information at least in that the first comment entered in thefirst text entry interface is shared with the second user withoutreceiving, from the first user, any indication of identity of the seconduser.
 58. The method of claim 52 wherein the computer-based servicesending the first comment to the second user based, at least in part, onthe second specification of interest.
 59. The method of claim 52wherein: receiving the first specification of interest includesreceiving specification of interest in occurrence of a particular changeto the particular information; and the at least one information updatecaused the particular change to the particular information.
 60. Themethod of claim 59 wherein the second information includes descriptionof the particular change.
 61. One or more non-transitorycomputer-readable media storing instructions which, when executed by oneor more processors, cause the one or more processors to perform themethod recited in any one of claims1,3,4,10,11,15,17,19,39,44-45,52,54,55,56.
 62. An apparatus, comprisingone or more processors, including a plurality of means, wherein theplurality of means includes means for performing each step of the methodrecited in any one of claims 10,11,15,19,39,44-45,52.
 63. An apparatuscomprising one or more processors, one or more memories, and one or moresequences of instructions that are stored in the one or more memories,wherein each memory from the one or more memories is operatively coupledto at least one of the one or more processors, and wherein the one ormore sequences of instructions, when performed by the one or moreprocessors, cause the one or more processors to execute the steps of themethod recited in any one of claims1,3-5,8,9-11,14,15,17,19-20,23,31-35, 39-43,44-45,52,53,56,59.